Add the latest recommended passing tokens approach #35482
+229
β10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #31691
Addresses #35225
As usual, the updates are based on π¦ RexHacks!β’ π, so get ready for some potential code smells π©ππ that we'll need to fix.
A couple of items to discuss for resolving this ...
WRT getting the access token out of the cookie ...
That line doesn't seem to be removing the access token because the access token can still be obtained in
ValidateOrRefreshCookieAsync
, which is called afterOnSigningIn
. Is that the wrong way to remove the access token from the cookie? [It's on the PR in spite of being a no-op at the moment.]You suggested ...
When I injected
AuthenticationStateProvider
into theServerWeatherForecaster
and tried to use it ...... it throws when calling
GetAuthenticationStateAsync
stating ...Therefore, I went back to getting the claim from
HttpContext
, which is working π and on the PR.Internal previews